<div id="Getting-the-source"></div>
<div class="header">
<p>
Next: [[cvs: Committing your changes#Committing your changes|Committing your changes]], Up: [[cvs: A sample session#A sample session|A sample session]] &nbsp; |[[cvs: Index#SEC_Contents|Contents]]||[[cvs: Index#Index|Index]]|</p>
</div>

----

<div id="Getting-the-source-1"></div>
==== Getting the source ====
<div id="index-Getting-the-source"></div>
<div id="index-Checking-out-source"></div>
<div id="index-Fetching-source"></div>
<div id="index-Source_002c-getting-from-CVS"></div>
<div id="index-Checkout_002c-example"></div>

The first thing you must do is to get your own working copy of the
source for &lsquo;<code>tc</code>&rsquo;.  For this, you use the <code>checkout</code> command:

<div class="example" style="margin-left: 3.2em">
 $ cvs checkout tc
</div>

This will create a new directory called &lsquo;<tt>tc</tt>&rsquo; and populate it with
the source files.

<div class="example" style="margin-left: 3.2em">
 $ cd tc
 $ ls
 CVS         Makefile    backend.c   driver.c    frontend.c  parser.c
</div>

The &lsquo;<tt>CVS</tt>&rsquo; directory is used internally by
<small>CVS</small>.  Normally, you should not modify or remove
any of the files in it.

You start your favorite editor, hack away at &lsquo;<tt>backend.c</tt>&rsquo;, and a couple
of hours later you have added an optimization pass to the compiler.
A note to <small>RCS</small> and <small>SCCS</small> users: There is no need to lock the files that
you want to edit.  See [[cvs: Multiple developers#Multiple developers|Multiple developers]], for an explanation.

This document was generated on <i>a sunny day</i> using [http://www.nongnu.org/texi2html/ <i>texi2html</i>].
